home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CU Amiga Super CD-ROM 1
/
CU Amiga Magazine CD-ROM Special Edition (1995)(EMAP Images)(GB)[Issue 1995-11].iso
/
Aminet
/
comm
/
cnet
/
RRR_RH02.lha
/
Hydra
/
RHydra.doc
< prev
next >
Wrap
Text File
|
1995-04-26
|
8KB
|
227 lines
R.R.R's
R A I N B O W H Y D R A v0.2 for CNET/3
Based on Flux Point FPHydra v0.2, thanks boys
Released 26.apr.95
0. License Agreement
--------------------
I know everyone will be craving on editing Rainbow Hydra, as it's ARexx.
Everyone is always editing arexx-scripts to suit their needs and
releasing their own versions.
EDITING IS ALLOWED, IN CASE YOU a) Change the name of the product
b) Tell that it's based on our product
c) Upload your product into AMINET
If you won't... Well, you're just an ultimate asshole you know.
There is almost nothing more we dislike than those "fucking cool
elite dudes" who create "new" versions, take all the credit and
limit the distribution to couple of shitty "elite" BBSes.
Of course making own versions is ideal only if this version doesn't
work or it lacks some really serious things. Anyway, we suggest that
you first email us, requesting the features you need. If we don't
agree to do them, well, do your own version then. :)
This program is freeware. We are not responsible for anything
the use or misuse of this program might cause. You're on your own, boy.
1. Why?
-------
The Flux Point Hydra was a bogus. It lacked several useful functions
and as a matter of fact, it didn't even work with two different CNet
systems we tested it on. The source code seemed to be somewhat crappy
and full of unnecessary things (If FP boys are reading this, check
for example what that do4;getchar;end-thing did. Yep, nothing. It
was the bufferflush which removed the a's you dimwits...) :)
And why we didn't mail these suggestions and stuff to you? Simple.
NO EMAIL ADDRESS! No proper documentation - Just some semiscene-
bragging.
2. What?
--------
This is a Hydra daemon for CNet, using Olaf Barthel's HydraCom
revision 5 (which is included). It will propably work with future
Hydracom versions as well.
With Hydra-protocol, your users can simultaneously upload, download
and chat with SysOp without a big loss on CPS side.
There is a drawback in CNet - There is no easy way (or atleast a
way anyone has publicly discovered! IF YOU KNOW ONE, PLEASE EMAIL
US!) to ADD files to CNet filelistings via ARexx. So the uploads
through Hydra will end up to a directory, where they can be adopted
by SysOp or auto-maintenance. (For those who love to remove credits
this will be a major disaster as all files seem to be uploaded by
SysOp or auto-maintenance!) Well, it's THANX KEN! (Not our fault)
Rainbow Hydra will kindly ask filenote-lenght descriptions for each
upload, write 'em as filenotes, and when adopted, they will end up
as descriptions.
It will also adjust all the credits and stuff of the user according
to the last transfer. RHydra will use User's Default Ratio #1 for
credit awarding/distracting.
3. Installation
---------------
· Extract the RHydra archive to PFILES:
· Add this to your BBSMENU under '4; ud/base' :
HYDRA | #0PFiles:Hydra/RHydra.rexx}
· After that, edit the RHydra.rexx to suit your needs. You will have
to change various self-explanatory config things. We suggest that you
create a special subboard for Hydra-uploads (global Hydra UL dir),
which will automatically adopt the orphan files during the automaintenance.
If you use current dir, uploads will end to the area where user starts Hydra.
· You may want to edit the pfiles:hydra/banner.txt to suit your needs.
It's shown before transfer. Upload rules perhaps?
· Then extract HydraCom5.lha to PFILES:HYDRA/ directory. Only the
HydraCom executable is necessary for RHydra operation.
· Also edit your systext: files to contain the HYDRA command. :)
· Remember that you will need sort, filenote and delete commands
somewhere on your path.
4. Usage
--------
One selects the files to be downloaded with * command, and then
types HYDRA at any file prompt. After that, user should start his/her
own HydraCOM. Uploads have to be chosen before Hydra-transfer is started.
Note that select buffer will be cleared every time Hydra is started.
See "Todo/limitations"-section.
5. Problems
-----------
We have experienced some problems on bi-dir transfers with some weird
serial cards. If such problems (full speed transfer to other direction,
and almost nothing to another) occur, we can't help you. Check your serial
card manual and everything else that might be the cause. Anyway, those
problems are caused by either HydraCom or your serial, not RHydra.
Remember that bi-dir transfer won't work on plain a HST connection.
(14.4k to other dir and something like 300bps to another)
6. History
----------
New in RHydra v0.2
· Banner.txt, which is shown before Hydra transfer (Upload rules?)
· Optional upload time return/reward
· Option to remove user's uploads from his downloads-today. This means that
when he uploads, he can download the size of his upload more than his daily
download limit allows. Both files & bytes counted.
· Infinite (0) daily download limits are now recognized. Thanks Grande Zumba!
· Free downloads are now noticed, and not distracted from credits. User can
download endless amounts of free downloads/day, only limited by time-limit.
· Optionally displays selected files at startup (Same as SS-command)
Changes since FPHydra v0.2
· Informs if there is some CNet config error (Not just quit like before)
· Takes a note of infinite file or byte credits
· Asks users to describe uploads, and deposits descriptions as filenotes
· Informs about skipped files if user has not enough credz
or if user has downloaded "enough" today.
· Transfer totals
· It's possible to use Global Hydra UL dir for all uploads
· Uploads have now current file date
· Modifies user statistics according to transfer
· Crude logging to calls, uloads & dloads
· Lots of cosmetic changes :)
7. Todo/Limitations
-------------------
· We don't know how to add files to CNet filelistings with ARexx.
So the uploads will just end up in some directory and have to be
picked up by SysOp or automaintenance.
· On startup, Hydra will always clean the select buffer, no matter
if the files haven't been downloaded or if they've been skipped.
In order to make the routine more sensitive, we need to know how
to edit select buffer with Arexx.
If you have any idea how to make these, please email rrr@klinja.fipnet.fi
Also all suggestions of enhancements are really welcome.
8. Contact
----------
We can be contacted by emailing rrr@klinja.fipnet.fi ... Don't hesitate! :)
R.R.R. BBS-Service is also available,
Kevyt Linja +358-0-343-3193 & +358-0-343-2373
9. Original FPHydra "documentation"
-----------------------------------
REMEMBER THAT FLUX POINT DUDES ARE IN NO WAY RESPONSIBLE FOR THE STUFF
RAINBOW HYDRA DOES. OF COURSE WE ARE NOT RESPONSIBLE EITHER. THIS IS
FREEWARE, REMEMBER. ANYWAY - FLAME US, NOT THEM. THANKS.
/********** Automaticly generated header, don't edit ************************
*
* PROGRAM: FPHydra.rexx
*
* PURPOSE: Interface between CNet and Hydracom.
*
* DATE: 09 Mar 95
*
* TIME: 19:33:03
*
* VERSION: 0
* REVISION: 2
* SUBREVISION: 0
* CNET VERSION: 3.05c
*
* LOG:
*
* 09 Mar 95 Added a crude routine to deduct credit for downloads, and
* reward credit for uploads.
* Found a Getuser to disable the Idle Timer, since Hydracom
* detaches from Cnet, so the port will be idle.
*
* 14 Jan 95 First version.
*
*
* INSTALLATION:
*
* Add this to your BBSMENU under '4; ud/base' :
*
* HYDRA | #0PFiles:FPHydra.rexx}
*
*
* ==========================================================================
*
* Another
* _____ __ __ __ __ __ ___ ____ __ __ __ ______
* / ___// / / / / / \ \/ / / _ \ / __ \ / // \/ //_ __/
* / __/ / /__ / /_/ / / / / ___// /_/ // // /\ / / /
* /_/ /____/ \____/ /_/\_\ /_/ \____//_//_/ /_/ /_/
*
* P R O D U C T I O N
*
* Call +45 3526-2527 FIDO 2:235/202.0 CLINK 912:2000/4.0
*
***************************************************************************/